Long preamble and duty cycle based coexistence mechanism for power line communication (PLC) networks

ABSTRACT

Embodiments of methods and systems for supporting coexistence of multiple technologies in a Power Line Communication (PLC) network are disclosed. A long coexistence preamble sequence may be transmitted by a device that has been forced to back off the PLC channel multiple times. The long coexistence sequence provides a way for the device to request channel access from devices on the channel using other technology. The device may transmit a data packet after transmitting the long coexistence preamble sequence. A network duty cycle time may also be defined as a maximum allowed duration for nodes of the same network to access the channel. When the network duty cycle time occurs, all nodes will back off the channel for a duty cycle extended inter frame space before transmitting again. The long coexistence preamble sequence and the network duty cycle time may be used together.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority U.S. patentapplication Ser. No. 16/552,911, filed on Aug. 27, 2019, which is acontinuation to U.S. patent application Ser. No. 15/946,041, filed onApr. 5, 2018 (now U.S. Pat. No. 10,396,852), which is a continuation ofand claims priority to U.S. patent application Ser. No. 14/824,506,filed on Aug. 12, 2015 (now U.S. Pat. No. 9,941,929), which is acontinuation of and claims priority to U.S. patent application Ser. No.13/910,125, filed on Jun. 5, 2013 (now issued U.S. Pat. No. 9,136,908),which claims the benefit of the filing date of U.S. Provisional PatentApplication No. 61/655,558, which is titled “Long Preamble and DutyCycle based Coexistence Mechanism for Power Line Communication PLCNetworks” and was filed on Jun. 5, 2012, the disclosures of which arehereby incorporated by reference herein in their entireties.

BACKGROUND

Power line communications (PLC) include systems for communicating dataover the same medium that is also used to transmit electric power toresidences, buildings, and other premises, such as wires, power lines,or other conductors. In its simplest terms, PLC modulates communicationsignals over existing power lines. This enables devices to be networkedwithout introducing any new wires or cables. This capability isextremely attractive across a diverse range of applications that canleverage greater intelligence and efficiency through networking. PLCapplications include utility meters, home area networks, and applianceand lighting control.

PLC is a generic term for any technology that uses power lines as acommunications channel. Various PLC standardization efforts arecurrently in work around the world. The different standards focus ondifferent performance factors and issues relating to particularapplications and operating environments. Two of the most well-known PLCstandards are G3 and PRIME. G3 has been approved by the InternationalTelecommunication Union (ITU). IEEE is developing the IEEE P1901.2standard that is based on G3. Each PLC standard has its own uniquecharacteristics.

Using PLC to communicate with utility meters enables applications suchas Automated Meter Reading (AMR) and Automated Meter Infrastructure(AMI) communications without the need to install additional wires.Consumers may also use PLC to connect home electric meters to an energymonitoring device or in-home display monitor their energy consumptionand to leverage lower-cost electric pricing based on time-of-day demand.

As the home area network expands to include controlling home appliancesfor more efficient consumption of energy, OEMs may use PLC to link thesedevices and the home network. PLC may also support home and industrialautomation by integrating intelligence into a wide variety of lightingproducts to enable functionality such as remote control of lighting,automated activation and deactivation of lights, monitoring of usage toaccurately calculate energy costs, and connectivity to the grid.

The manner in which PLC systems are implemented depends upon localregulations, characteristics of local power grids, etc. The frequencyband available for PLC users depends upon the location of the system. InEurope, PLC bands are defined by the CENELEC (European Committee forElectrotechnical Standardization). The CENELEC-A band (3 kHz-95 kHz) isexclusively for energy providers. The CENELEC-B, C, D bands are open forend user applications, which may include PLC users. Typically, PLCsystems operate between 35-90 kHz in the CENELEC A band using 36 tonesspaced 1.5675 kHz apart. In the United States, the FCC has conductedemissions requirements that start at 535 kHz and therefore the PLCsystems have an FCC band defined from 154-487.5 kHz using 72 tonesspaced at 4.6875 kHz apart. In other parts of the world differentfrequency bands are used, such as the Association of Radio Industriesand Businesses (ARIB)-defined band in Japan, which operates at 10-450kHz, and the Electric Power Research Institute (EPRI)-defined bands inChina, which operates at 3-90 kHz.

Different groups of nodes in a PLC network may use differenttechnologies. For example, a first group of nodes may use a firstprotocol or standard to communicate, and a second group of nodes may usea second protocol or standard to communicate. Although the nodes usingthe different technologies may not attempt to communicate with eachother, they may cause interference with each other on the PLC network.Depending upon the back-off method used in the channel access protocolsfor each technology, one technology may effectively block the othertechnology from the channel.

SUMMARY OF THE INVENTION

Embodiments of the invention support coexistence between two similar PLCtechnologies that rely on preamble detection to access a communicationchannel. The invention provides fairness to both technologies using acombination of a duty-cycle approach and a long-preamble approachensures that both PLC technologies share the channel. The duty-cycleapproach is non-intrusive in that it does not add to network overhead.The long-preamble approach may be intrusive by impacting networkthroughput.

In one embodiment, a system and method for supporting coexistence ofdifferent technologies on a power line communication network isdisclosed. A power line communication device detects a coexistencepreamble transmitted from a remote device on a channel in a PLC network.The device determines whether a threshold back-off duration has beenreached. The device transmits a coexistence preamble sequence inresponse to a determination that the threshold back-off duration hasbeen reached. The device may transmit a data frame on the channel aftertransmitting the coexistence preamble sequence.

The coexistence preamble sequence may comprise two or more repeatedcoexistence preambles. A size of the coexistence preamble sequence maybe selected based upon a maximum packet size for the PLC device. Thethreshold back-off duration may be defined as a predetermined number Nof coexistence Extended Interframe Space (cEIFS) durations for the PLCnetwork.

The device may further determine that a first coexistence preamblesequence has been transmitted on the channel. The device then delaystransmission of a second coexistence preamble sequence on the channelfor at least a threshold back-off duration.

In another embodiment, a power line communication device monitors achannel occupancy duration during which devices transmit on a channel ina PLC network. The device determines when the channel occupancy durationexceeds a network duty cycle time (ndcTime). The device then backs offfrom the channel for a duty cycle Extended Interframe Space (dcEIFS)duration when the channel occupancy duration exceeds ndcTime.

The values for the ndcTime and dcEIFS parameters may be selected basedupon channel access technologies used by PLC devices on the PLC network.The values of ndcTime and N may be selected so that ndcTime is less thanthe value of (N×EIFS).

In other embodiments, the value of ndcTime and (N×cEIFS) can be selectedto give precedence to a particular approach. For example, ndcTime may beselected as less than N×cEIFS to give precedence to duty cycle approach,or N×cEIFS may be selected as less than ndcTime to give precedence to along cycle approach.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, wherein:

FIG. 1 is a diagram of a PLC system according to some embodiments.

FIG. 2 is a block diagram of a PLC device or modem according to someembodiments.

FIG. 3 is a block diagram of a PLC gateway according to someembodiments.

FIG. 4 is a block diagram of a PLC data concentrator according to someembodiments.

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem configured for point-to-point PLC.

FIG. 6 is a block diagram of an integrated circuit according to someembodiments.

FIG. 7 illustrates an example embodiment of a PLC network for a localutility PLC communications system.

FIG. 8 illustrates a network neighborhood having devices that use twodifferent technology parameters.

FIG. 9 illustrates an example PLC network having PLC nodes using a firsttechnology and PLC nodes using a second technology.

FIG. 10 illustrates a long coexistence preamble sequence according toone embodiment.

FIG. 11 illustrates an example method that may be used to determine thetransmission of a long coexistence preamble sequence.

FIG. 12 illustrates a method for using a network duty cycle time by apower line communication device according to one embodiment.

DETAILED DESCRIPTION

The invention now will be described more fully hereinafter withreference to the accompanying drawings. This invention may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the invention to those skilled in the art. Oneskilled in the art may be able to use the various embodiments of theinvention.

FIG. 1 illustrates a power line communication network according to someembodiments. Medium voltage (MV) power lines 103 from subnode 101typically carry voltage in the tens of kilovolts range. Transformer 104steps the MV power down to low voltage (LV) power on LV lines 105,carrying voltage in the range of 100-240 VAC. Transformer 104 istypically designed to operate at very low frequencies in the range of50-60 Hz. Transformer 104 does not typically allow high frequencies,such as signals greater than 100 KHz, to pass between LV lines 105 andMV lines 103. LV lines 105 feed power to customers via meters or nodes106 a-n, which are typically mounted on the outside of residences 102a-n. Although referred to as “residences,” premises 102 a-n may includeany type of building, facility, electric vehicle charging node, or otherlocation where electric power is received and/or consumed. A breakerpanel, such as panel 107, provides an interface between meter 106 n andelectrical wires 108 within residence 102 n. Electrical wires 108deliver power to outlets 110, switches 111 and other electric deviceswithin residence 102 n.

The power line topology illustrated in FIG. 1 may be used to deliverhigh-speed communications to residences 102 a-n. In someimplementations, power line communications modems or gateways 112 a-nmay be coupled to LV power lines 105 at meter 106 a-n. PLCmodems/gateways 112 a-n may be used to transmit and receive data signalsover MV/LV lines 103/105. Such data signals may be used to supportmetering and power delivery applications (e.g., smart gridapplications), communication systems, high speed Internet, telephony,video conferencing, and video delivery, to name a few. By transportingtelecommunications and/or data signals over a power transmissionnetwork, there is no need to install new cabling to each subscriber 102a-n. Thus, by using existing electricity distribution systems to carrydata signals, significant cost savings are possible.

An illustrative method for transmitting data over power lines may use acarrier signal having a frequency different from that of the powersignal. The carrier signal may be modulated by the data, for example,using an OFDM technology or the like described, for example, G3-PLCstandard.

PLC modems or gateways 112 a-n at residences 102 a-n use the MV/LV powergrid to carry data signals to and from PLC data concentrator or router114 without requiring additional wiring. Data concentrator or router 114may be coupled to either MV line 103 or LV line 105. Modems or gateways112 a-n may support applications such as high-speed broadband Internetlinks, narrowband control applications, low bandwidth data collectionapplications, or the like. In a home environment, for example, modems orgateways 112 a-n may further enable home and building automation in heatand air conditioning, lighting, and security. Also, PLC modems orgateways 112 a-n may enable AC or DC charging of electric vehicles andother appliances. An example of an AC or DC charger is illustrated asPLC device 113. Outside the premises, power line communication networksmay provide street lighting control and remote power meter datacollection.

One or more PLC data concentrators or routers 114 may be coupled tocontrol center 130 (e.g., a utility company) via network 120. Network120 may include, for example, an IP-based network, the Internet, acellular network, a WiFi network, a WiMax network, or the like. As such,control center 130 may be configured to collect power consumption andother types of relevant information from gateway(s) 112 and/or device(s)113 through concentrator(s) 114. Additionally or alternatively, controlcenter 130 may be configured to implement smart grid policies and otherregulatory or commercial rules by communicating such rules to eachgateway(s) 112 and/or device(s) 113 through concentrator(s) 114.

FIG. 2 is a block diagram of PLC device 113 according to someembodiments. As illustrated, AC interface 201 may be coupled toelectrical wires 108 a and 108 b inside of premises 112 n in a mannerthat allows PLC device 113 to switch the connection between wires 108 aand 108 b off using a switching circuit or the like. In otherembodiments, however, AC interface 201 may be connected to a single wire108 (i.e., without breaking wire 108 into wires 108 a and 108 b) andwithout providing such switching capabilities. In operation, ACinterface 201 may allow PLC engine 202 to receive and transmit PLCsignals over wires 108 a-b. In some cases, PLC device 113 may be a PLCmodem. Additionally or alternatively, PLC device 113 may be a part of asmart grid device (e.g., an AC or DC charger, a meter, etc.), anappliance, or a control module for other electrical elements locatedinside or outside of premises 112 n (e.g., street lighting, etc.).

PLC engine 202 may be configured to transmit and/or receive PLC signalsover wires 108 a and/or 108 b via AC interface 201 using a particularfrequency band. In some embodiments, PLC engine 202 may be configured totransmit OFDM signals, although other types of modulation schemes may beused. As such, PLC engine 202 may include or otherwise be configured tocommunicate with metrology or monitoring circuits (not shown) that arein turn configured to measure power consumption characteristics ofcertain devices or appliances via wires 108, 108 a, and/or 108 b. PLCengine 202 may receive such power consumption information, encode it asone or more PLC signals, and transmit it over wires 108, 108 a, and/or108 b to higher-level PLC devices (e.g., PLC gateways 112 n, dataaggregators 114, etc.) for further processing. Conversely, PLC engine202 may receive instructions and/or other information from suchhigher-level PLC devices encoded in PLC signals, for example, to allowPLC engine 202 to select a particular frequency band in which tooperate.

FIG. 3 is a block diagram of PLC gateway 112 according to someembodiments. As illustrated in this example, gateway engine 301 iscoupled to meter interface 302, local communication interface 304, andfrequency band usage database 304. Meter interface 302 is coupled tometer 106, and local communication interface 304 is coupled to one ormore of a variety of PLC devices such as, for example, PLC device 113.Local communication interface 304 may provide a variety of communicationprotocols such as, for example, ZigBee, Bluetooth, Wi-Fi, Wi-Max,Ethernet, etc., which may enable gateway 112 to communicate with a widevariety of different devices and appliances. In operation, gatewayengine 301 may be configured to collect communications from PLC device113 and/or other devices, as well as meter 106, and serve as aninterface between these various devices and PLC data concentrator 114.Gateway engine 301 may also be configured to allocate frequency bands tospecific devices and/or to provide information to such devices thatenable them to self-assign their own operating frequencies.

In some embodiments, PLC gateway 112 may be disposed within or nearpremises 102 n and serve as a gateway to all PLC communications toand/or from premises 102 n. In other embodiments, however, PLC gateway112 may be absent and PLC devices 113 (as well as meter 106 n and/orother appliances) may communicate directly with PLC data concentrator114. When PLC gateway 112 is present, it may include database 304 withrecords of frequency bands currently used, for example, by various PLCdevices 113 within premises 102 n. An example of such a record mayinclude, for instance, device identification information (e.g., serialnumber, device ID, etc.), application profile, device class, and/orcurrently allocated frequency band. As such, gateway engine 301 may usedatabase 305 in assigning, allocating, or otherwise managing frequencybands assigned to its various PLC devices.

FIG. 4 is a block diagram of PLC data concentrator or router 114according to some embodiments. Gateway interface 401 is coupled to dataconcentrator engine 402 and may be configured to communicate with one ormore PLC gateways 112 a-n. Network interface 403 is also coupled to dataconcentrator engine 402 and may be configured to communicate withnetwork 120. In operation, data concentrator engine 402 may be used tocollect information and data from multiple gateways 112 a-n beforeforwarding the data to control center 130. In cases where PLC gateways112 a-n are absent, gateway interface 401 may be replaced with a meterand/or device interface (now shown) configured to communicate directlywith meters 116 a-n, PLC devices 113, and/or other appliances. Further,if PLC gateways 112 a-n are absent, frequency usage database 404 may beconfigured to store records similar to those described above withrespect to database 304.

FIG. 5 is a schematic block diagram illustrating one embodiment of asystem 500 configured for point-to-point PLC. The system 500 may includea PLC transmitter 501 and a PLC receiver 502. For example, a PLC gateway112 may be configured as the PLC transmitter 501 and a PLC device 113may be configured as the PLC receiver 502. Alternatively, the PLC device113 may be configured as the PLC transmitter 501 and the PLC gateway 112may be configured as the PLC receiver 502. In still a furtherembodiment, the data concentrator 114 may be configured as either thePLC transmitter 501 or the PLC receiver 502 and configured incombination with a PLC gateway 112 or a PLC device 113 in apoint-to-point system 500. In still a further embodiment, a plurality ofPLC devices 113 may be configured to communicate directly in apoint-to-point PLC system 500 as described in FIG. 5 . Additionally, thesubnode 101 may be configured in a point-to-point system 500 asdescribed above. On of ordinary skill in the art will recognize avariety of suitable configurations for the point-to-point PLC system 500described in FIG. 5 .

FIG. 6 is a block diagram of a circuit for implementing the transmissionof multiple beacon frames using different modulation techniques on eachtone mask in a PLC network according to some embodiments. In some cases,one or more of the devices and/or apparatuses shown in FIGS. 1-5 may beimplemented as shown in FIG. 6 . In some embodiments, processor 602 maybe a digital signal processor (DSP), an application specific integratedcircuit (ASIC), a system-on-chip (SoC) circuit, a field-programmablegate array (FPGA), a microprocessor, a microcontroller, or the like.Processor 602 is coupled to one or more peripherals 604 and externalmemory 603. In some cases, external memory 603 may be used to storeand/or maintain databases 304 and/or 404 shown in FIGS. 3 and 4 .Further, processor 602 may include a driver for communicating signals toexternal memory 603 and another driver for communicating signals toperipherals 604. Power supply 601 provides supply voltages to processor602 as well as one or more supply voltages to memory 603 and/orperipherals 604. In some embodiments, more than one instance ofprocessor 602 may be included (and more than one external memory 603 maybe included as well).

Peripherals 604 may include any desired circuitry, depending on the typeof PLC system. For example, in an embodiment, peripherals 604 mayimplement local communication interface 303 and include devices forvarious types of wireless communication, such as Wi-Fi, ZigBee,Bluetooth, cellular, global positioning system, etc. Peripherals 604 mayalso include additional storage, including RAM storage, solid-statestorage, or disk storage. In some cases, peripherals 604 may includeuser interface devices such as a display screen, including touch displayscreens or multi-touch display screens, keyboard or other input devices,microphones, speakers, etc.

External memory 603 may include any type of memory. For example,external memory 603 may include SRAM, nonvolatile RAM (NVRAM, such as“flash” memory), and/or dynamic RAM (DRAM) such as synchronous DRAM(SDRAM), double data rate (DDR, DDR2, DDR3, etc.) SDRAM, DRAM, etc.External memory 603 may include one or more memory modules to which thememory devices are mounted, such as single inline memory modules(SIMMs), dual inline memory modules (DIMMs), etc.

FIG. 7 illustrates an example embodiment of a PLC network 700 for alocal utility PLC communications system. Network 700 includes LV nodes702 a-n and each of the nodes 702 a-n is connected to MV power line 720through a corresponding transformer 710 a-n and LV line 706 a-n. Router,or modem, 714 is also connected to MV power line 720. A sub-network 728,or neighborhood 728, may be represented by the combination of nodes 702a-n and router 714. Master router 712 and router 716 are also connectedto MV line 720, which is powered by power grid 722. Power grid 722represents the high voltage power distribution system.

Master router 712 may be the gateway to telecommunications backbone 724and local utility, or control center, 726. Master router 712 maytransmit data collected by the routers to the local utility 726 and mayalso broadcast commands from local utility 726 to the rest of thenetwork. The commands from local utility 726 may require data collectionat prescribed times, changes to communication protocols, and othersoftware or communication updates.

During UL communications, the nodes 702 a-n in neighborhood 728 maytransmit usage and load information (“data”) through their respectivetransformer 710 a-n to the MV router 714. In turn, router 714 forwardsthis data to master router 712, which sends the data to the utilitycompany 726 over the telecommunications backbone 724. During DLcommunications (router 714 to nodes 702 a-n) requests for data uploadingor commands to perform other tasks are transmitted.

In accordance with various embodiments, nodes 702 a-n may be devicesusing different standards or protocols that operate together incoexistence. In PLC networks where there are several different deviceswith different technology parameters (e.g., devices using one of IEEEP1901.2 FCC-low band, IEEE P1901.2 CEN-A, and IEEE P1901.2 FCC, G.hnem),a common back-off time for all devices 702 a-n in thenetwork-coexistence Extended Inter Frame Space (cEIFS)—may be defined. Adevice 702 n will back-off for a cEIFS interval if the device 702 ndetects a coexistence preamble but does not detect the device 702 n'sown native preamble. In one embodiment, cEIFS may be a Personal AreaNetwork (PAN)-specific parameter.

In other embodiments, the system may include devices operating accordingto different standards or protocols that all communication onFCC-assigned frequencies. For example, the system may include G3 devicesthat operate according to ITU or IEEE standards, such as IEEE P1901.2.The system may also include devices that operate according to the PRIMEstandard. The present embodiments may also enable coexistence betweenthese devices.

In a network with devices operating with two or more differenttechnology parameters, devices from one technology may dominate networkaccess.

Table 1 illustrates example band plans that may be used by nodes havingdifferent technologies.

TABLE 1 Band-Plan Band-Frequencies 1 IEEE P1901.2 FCC Band 154.6875kHz-487.5 kHz 2 ITU-G3 ARM Band 154.6875 kHz-403 kHz   3 ITU-G3 FCC1Band 154.6875 kHz-262 kHz   4 ITU-G.hnem FCC Band   35 kHz-480 kHz 5IEEE P1901.2 FCC Multitone 36-1 154.6875 kHz-318 kHz   6 IEEE P1901.2FCC Multitone 36-2    323 kHz-487.5 kHz 7 IEEE P1901.2 FCC Low Band    37.5 kHz-121.875 kHz 8 IEEE/G3 CEN-A   35 kHz-90 kHz 9 PRIME CEN-A    kHz-88.8 kHz

FIG. 8 illustrates a network neighborhood 800 having devices 801, 802operating with two different technology parameters. Devices 801communicate with technology 1 parameters, and devices 802 communicatewith technology 2 parameters. It may arise that devices using onetechnology may dominate network access. For example, communication maybe dominated by devices 801 using technology 1 under the followingconditions:

-   -   a) if there is a presence of more devices 801 using technology 1        in network neighborhood 800; or    -   b) if cEIFS is a large value resulting in the devices 802 using        technology 2 continuously backing off.

Although the adaptive back-off scheme in the IEEE P1901.2 standardpenalizes a transmitter that wins the channel consecutively for severaltransmissions by choosing the maximum back-off value, there are stillscenarios for which fair channel access mechanisms are required.

In one scenario, fair channel access mechanisms are required when thereare multiple transmitters 801 using the same technology in a particularneighborhood 800 compared to few nodes 802 using an alternatetechnology. In this scenario, nodes 801 (using the same technology) maytake turns accessing the channel and consequently will never encounterthe state where a particular node 801 gets channel access consecutively.However, it is likely that these several nodes 801 together may haveacquired channel access consecutively. Mechanisms are needed to enablethe alternate technology nodes 802 to fairly contend for the channel ifthis scenario is encountered.

In other scenarios, a generic fair channel access methodology is neededto address technologies (e.g., other than IEEE P1901.2) that may notnecessarily penalize the winning transmitter after several successfulchannel accesses. The mechanisms may be agnostic of the underlyingchannel access mechanism for a specific technology.

FIG. 9 illustrates an example PLC network 900 having PLC nodes 901 usinga first technology and PLC nodes 902 using a second technology. Asdescribed in connection with FIG. 8 , if the technology 1 nodes 901outnumber the technology 2 nodes 902, then the technology 1 nodes 901may dominate the channel on power line 903 thereby preventing technology2 nodes 902 from accessing the channel.

A hybrid solution based upon a combination of a long coexistencepreamble and a defined network duty cycle is proposed to address thissituation.

Long Coexistence Preamble Approach

A long coexistence preamble sequence may be defined. An example of along coexistence preamble sequence 1000 is illustrated in FIG. 10 . Thelong coexistence preamble sequence 1000 consists of m repeated preambles(e.g., syncC symbols) 1001 a-m. The value of m can be selected such thatthe long coexistence preamble sequence 1000 is as large as the maximumpacket size supported by a selected technology. The syncC symbol may bedefined as any appropriate synchronization symbol, such as one or moreof the syncP and/or syncM synchronization symbols defined in the IEEEP1901.2 standard. Alternatively, the syncC symbol may be a genericsynchronization symbol across different technologies and may correspondto either a chirp signal or known sequence of +/−1's.

FIG. 11 illustrates an example method that may be used to determine thetransmission of a long coexistence preamble sequence.

In step 1101, devices using a first technology (technology 1) and asecond technology (technology 2) attempt to access a PLC channel usingthe appropriate access method for their respective technologies.

In step 1102, a device using technology 2 will back off for anadditional duration of cEIFS, if the device detects a coexistencepreamble and does not detect its native preamble while in cEIFS period.

In step 1103, if a device from technology 2 has attempted to access thechannel N times for transmission and has backed off for N cEIFSdurations, then the device may transmit a long coexistence preamblesequence, such as the long coexistence preamble sequence 1000 definedabove and illustrated in FIG. 10 . Transmission of the long coexistencepreamble sequence is a way of “requesting” channel access from devicesof the different technologies (e.g., technology 1) that are using thechannel. The idea here is that if the long coexistence preamble sequenceis long enough, then there will be a time slot in which only the longcoexistence preamble sequence is present in the channel. This willresult in the devices that are using technology 1 to back off (for acEIFS interval) and thereby “releasing” the channel.

In step 1104, the technology 2 device may transmit a data frame afterthe long coexistence preamble sequence.

In step 1105, subsequent channel accesses may be subject to eachrespective technology's channel access mechanisms. For example,technology 1 nodes may contend after the cEIFS duration.

In step 1106, on receiving the long coexistence preamble sequence (e.g.,more than 2 coexistence preambles), all service nodes irrespective ofthe technology used will not send any other long coexistence preamblesequences for the next N×cEIFS. This ensures that there is no more than1 long coexistence preamble sequence in a sensing region every N×cEIFS.

Duty Cycle

A Network Duty Cycle (ndcTime) parameter may be defined as the maximumallowed duration for nodes of the PLC network to occupy the channel.After the ndcTime, all nodes of that network will backoff the channelfor a duty cycle cEIFS (dcEIFS) before being allowed to transmit again.All technologies will have the same dcEIFS.

The ndcTime and dcEIFS parameters may be configurable to allow regionaland band settings that best match local requirements.

Note that if the ndcTime duration is on the order of a fewtransmissions, then there may be a loss in throughput for nodes usingone type of technology. On the other hand, if the ndcTime duration istoo large, then there may not be a guarantee that nodes using anothertype of technology will have a transmission to be made during that time.Hence an optimum value should be selected for the ndcTime parameter.

FIG. 12 illustrates a method for using a network duty cycle time by apower line communication device according to one embodiment. In step1201, a channel occupancy duration is monitored. The channel occupancyduration represents a time during which devices transmit on a channel ina PLC network. In step 1202, the PLC device determines when the channeloccupancy duration exceeds a network duty cycle time (ndcTime). In step1203, the PLC device backs off from the channel for a duty cycleExtended Interframe Space (dcEIFS) duration when the channel occupancyduration exceeds the ndcTime.

Overall Solution

A node may be capable of performing either or both of the abovementioned solutions. Also, it is recommended to choose the ndcTime and Nparameters such that ndcTime<N×cEIFS.

It is to be noted that if the duty cycling with ndcTime allows atechnology 2 node to get access to channel, then the node will not beneeded to transmit a long preamble (i.e., a N×cEIFS time of non-accessto channel will not happen).

Also, if even after duty cycling, a technology 2 node does not getaccess to the channel, then that node will send a long preamble afterN×cEIFS.

The values of the ndcTime and N may be selected depending upon the typesof technology used by the nodes in the network. The rate at which thesesolutions are used can be controlled by the choice of these parametersat deployment. At deployment, if it is intended that the duty basedsolution alone is to be used, then the value of N can be set to a largevalue. On the other hand, at deployment the duty cycle approach can bedisabled by choosing ndcTime>N×cEIFS.

Many modifications and other embodiments of the invention(s) will cometo mind to one skilled in the art to which the invention(s) pertainhaving the benefit of the teachings presented in the foregoingdescriptions, and the associated drawings. Therefore, it is to beunderstood that the invention(s) are not to be limited to the specificembodiments disclosed. Although specific terms are employed herein, theyare used in a generic and descriptive sense only and not for purposes oflimitation.

What is claimed is:
 1. A method comprising: detecting, by a power linecommunication (PLC) device associated with a first protocol on a PLCnetwork, a first coexistence preamble; waiting, by the PLC device, aback-off duration before attempting a transmission on the PLC network;and in response to waiting the back-off duration: transmitting, by thePLC device on the PLC network, a long preamble that includes a number ofrepetitions of a second coexistence preamble, wherein the number ofrepetitions is determined by the PLC device such that the long preambleis at least as long as a largest packet supported by the PLC network;and subsequent to transmitting the long preamble, transmitting a dataframe on the PLC network.
 2. The method of claim 1, further comprising:attempting, by the PLC device, to access a channel on the PLC network.3. The method of claim 1, further comprising: detecting, by the PLCdevice, a third preamble with the first coexistence preamble and withoutdetecting a native preamble of the PLC device.
 4. The method of claim 2,wherein: for a time duration, the long preamble is the only longpreamble on the channel.
 5. The method of claim 1, wherein: the numberof repetitions is an integer.
 6. The method of claim 1, wherein: thelong preamble includes a synchronization symbol defined in IEEE P1901.2.7. The method of claim 6, wherein: the synchronization symbol is basedon a chirp signal or a known sequence of +/−1's.
 8. The method of claim1, wherein: the back-off duration is associated with the first protocol.9. The method of claim 1, wherein: the PLC device is associated with aset of technology parameters associated with the first protocol.
 10. Apower line communication (PLC) system comprising: a first deviceassociated with a first preamble and configured to communicate using afirst protocol of a plurality of protocols, the first device coupled toa PLC network; and a second device associated with a second preamble andconfigured to communicate using a second protocol of the plurality ofprotocols, the second device coupled to the PLC network; wherein thesecond device is configured to: in response to detecting a thirdpreamble and not detecting the second preamble, wait a first durationbefore accessing the PLC network; and in response to waiting a number ofdurations, wherein each of the number of durations is equal to the firstduration, transmit on the PLC network the third preamble and a dataframe associated with the second protocol.
 11. The PLC system of claim10, wherein: the first duration is associated with the second protocol;and the first duration is a coexistence Extended Inter Frame Space(cEIFS).
 12. The PLC system of claim 10, wherein the second device isconfigured to: determine an occupancy of a channel on the PLC network.13. The PLC system of claim 10, wherein: the third preamble includes asynchronization symbol defined in IEEE P1901.2.
 14. The PLC system ofclaim 10, wherein: the first protocol is one of IEEE P1901.2 FCC-lowband, IEEE P1901.2 CEN-A, and IEEE P1901.2 FCC G.hnem; the secondprotocol is one of IEEE P1901.2 FCC-low band, IEEE P1901.2 CEN-A, andIEEE P1901.2 FCC G.hnem; and the first protocol is different than thesecond protocol.
 15. The PLC system of claim 10, wherein: the thirdpreamble is at least as large as a largest packet associated with thePLC network.
 16. A communication device comprising: a transmitterconfigured to couple to a power line communication (PLC) network havinga maximum packet size; and circuitry configured to: detect a first datasequence that includes a first preamble without detecting a nativepreamble of the communication device; wait a back-off duration beforeattempting a transmission; and in response to waiting the back-offduration, transmit: a long preamble that includes a number ofrepetitions of the first preamble, wherein the number of repetitions isselected based on the maximum packet size; and subsequent to the longpreamble, a data frame.